Alternate alarm notifications based on battery condition

ABSTRACT

Systems and methods for smart alarms are provided. A computer-implemented method includes: receiving, by a computing device, an input including a set alarm time; determining, by the computing device, a battery drain condition of the computing device; and based on the determining the battery drain condition, performing a step including one of: sounding the alarm prior to the set alarm time based on determining that a user-defined condition is met at a time of the battery drain condition; displaying a message on the computing device indicating the battery drain condition; and providing an alternate alert based on a detected sleep stage of a user corresponding to a predefined acceptable sleep stage.

BACKGROUND

The present invention relates generally to alarms on mobile devices and,more particularly, to preventative and reactive alternative eventnotification methods for ensuring an alarm is provided when a mobiledevice powers off due to battery drain.

Mobile devices, such as smartphones, are commonly provided with an alarmclock application. The user of the mobile device can define alarmsettings in the alarm clock application including date, time, ringtone,and snooze settings. In this manner, the mobile device can be used inlieu of a traditional alarm clock. However, unlike a traditional alarmclock, a mobile device typically must have its battery recharged aboutonce a day. Given this frequency of battery drain and recharge formobile devices, it is common for a user to miss their alarm becausetheir mobile device runs out of battery charge prior to the time that isset for the alarm to sound.

For example, on a particular evening, a user may set the alarm on theirsmartphone for 6:00 AM the following morning. Between the time the usersets the alarm and the scheduled time of the alarm, the smartphone mayconsume all its battery power (e.g., by one or more other applicationsrunning on the smartphone during this time period before the scheduledtime of the alarm). In this scenario, due to the drained battery, thesmartphone turns off (powers off) prior to the scheduled time of thealarm. This results in the smartphone being off and thus not emittingthe alarm sound at the desired time of the alarm (e.g., at 6:00 AM inthis example). The user thus misses their alarm and might oversleep andmiss an event.

SUMMARY

In an aspect of the invention, there is a computer-implemented methodthat includes: receiving, by a computing device, an input comprising aset alarm time; and determining, by the computing device, a batterydrain condition of the computing device. The method includes, based onthe determining the battery drain condition, performing a stepcomprising one of: sounding the alarm prior to the set alarm time basedon determining that a user-defined condition is met at a time of thebattery drain condition; displaying a message on the computing deviceindicating the battery drain condition; and providing an alternate alertbased on a detected sleep stage of a user corresponding to a predefinedacceptable sleep stage.

In another aspect of the invention, there is a computer-implementedmethod including: receiving, by a computing device, preference data froma user device; and receiving, by the computing device, an alert from theuser device indicating a battery drain condition of the user device anda set alarm time of the user device. The method includes, based on thereceiving the alert, the computing device performing a step comprisingone of: sending a message to plural trusted user devices of members of abackup alarm group specified in the preference data, wherein the messageinstructs the members to provide an alternate alert to a user associatedwith the user device; determining a ranked list of the members of thebackup alarm group specified in the preference data, and sending themessage to the highest ranked member in the ranked list; sending acontrol command to a networked appliance specified in the preferencedata; and calling a landline telephone specified in the preference data.

In another aspect of the invention, there is a system comprising a CPU,a computer readable memory and a computer readable storage mediumassociated with a computing device. The system includes programinstructions to receive preference data from a user device. The systemincludes program instructions to receive an alert from the user deviceindicating a battery drain condition of the user device and a set alarmtime of the user device. The system includes program instructions to,based on the receiving the alert, perform a step comprising one of:sending a message to plural trusted user devices of members of a backupalarm group specified in the preference data, wherein the messageinstructs the members to provide an alternate alert to a user associatedwith the user device; determining a ranked list of the members of thebackup alarm group specified in the preference data, and sending themessage to the highest ranked member in the ranked list; sending acontrol command to a networked appliance specified in the preferencedata; and calling a landline telephone specified in the preference data.The program instructions are stored on the computer readable storagemedium for execution by the CPU via the computer readable memory.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in the detailed description whichfollows, in reference to the noted plurality of drawings by way ofnon-limiting examples of exemplary embodiments of the present invention.

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 shows a computing environment in accordance with aspects of theinvention.

FIGS. 5-10 show flowcharts of methods in accordance with aspects of theinvention.

DETAILED DESCRIPTION

The present invention relates generally to alarms on mobile devices and,more particularly, to preventative and reactive alternative eventnotification methods for ensuring an alarm is provided when a mobiledevice powers off due to battery drain. According to aspects of theinvention there is a smart alarm clock system that averts a failed alarmwhen a device runs out of power. In embodiments, the system employs bothpredictive and reactive methods to ensure that the user is woken up.Predictive methods may be used to prevent the user from setting an alarmon their device when it is determined that the device will run out ofbattery power before the time the alarm is set to ring. Reactive methodsmay employ alternative methods to wake up a user when the user's deviceruns out of battery power before the time the alarm is set to ring. Someprocesses of the invention may be implemented using an alarm app (e.g.,software application program) on the user's mobile device. Additionalprocesses of the invention may be implemented using an alarm serverconnected to the user's mobile device. The alarm server may be connectedto a cloud-based Internet of Things (IoT) network.

In embodiments, a system monitors the battery condition of an alarmdevice (e.g., smartphone), and implements one or more of the followingmethods when it is determined that a battery drain condition hasoccurred or will occur before the set time for the alarm to ring: causethe alarm device to ring the alarm earlier than the set alarm time whenthe battery drain condition occurs within a predefined threshold periodprior to the set alarm time; contact a trusted user and ask the trusteduser to use an alternative method to wake up an alarm user associatedwith the alarm device, e.g., by knocking on the alarm user's door,calling the alarm user's landline telephone, or turning on an IoT devicein the alarm user's space; cause an alarm server to automatically use analternative method to wake up the alarm user, e.g., by calling the alarmuser's landline telephone, or turning on an IoT device in the alarmuser's space; warning the alarm during setting the alarm when it ispredicted that the battery will drain before the set time of the alarm;and cause a wearable device of the alarm user to interrupt the alarmuser's sleep cycle.

Implementations of the invention may use a combination of plural ones ofthe methods described herein to prevent a missed alarm for a user. Asnoted herein, certain ones of the methods may be implemented using analarm app on the user's mobile device, and the user may set preferencesin the alarm app to define how they wish to respond to a drainingbattery condition that will affect an alarm. The alarm app may work incoordination with a power management app on a user's mobile device topermit the user to select optimal settings using a single button click.Advantageously, aspects of the inventive system may be implemented atthe application level without the need to make changes to operatingsystems or hardware.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowcharts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowcharts may represent a module, segment, or portion of instructions,which comprises one or more executable instructions for implementing thespecified logical function(s). In some alternative implementations, thefunctions noted in the block may occur out of the order noted in thefigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. It will also be noted that each block of the flowchartillustrations, and combinations of blocks in the flowchartillustrations, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts or carry outcombinations of special purpose hardware and computer instructions.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a nonremovable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and alarm management 96.

FIG. 4 shows a computing environment in accordance with aspects of theinvention. In embodiments, the environment comprises an alarm server 100running an alarm management module 102 that is configured to performcertain processes described herein. The alarm server 100 may be thecomputer system/server 12 of FIG. 1, and the alarm management module 102may be one of the program modules 42 running on the computersystem/server 12.

Still referring to FIG. 4, in aspects the computing environment alsoincludes a user device 104 running an alarm app 106 (e.g., a mobilesoftware application program) that is configured to perform certainprocesses described herein. In embodiments, the user device 104comprises a mobile computing device such as a smartphone, smart watch,tablet computer, or laptop computer. In embodiments, the user device 104comprises at least a processor, memory, display, user input device(e.g., touch screen and/or physical buttons), rechargeable battery,sound emitting device (e.g., speaker), and antenna for wirelesscommunication. In embodiments, the alarm app 106 is configured to permita user of the user device 104 to specify a date, time, and audible toneof an alarm (e.g., a wake-up alarm) in a conventional manner. Inaccordance with aspects of the invention, the alarm app 106 is alsoconfigured to monitor the battery charge status (e.g., battery percentremaining and/or estimated battery time remaining) of the user device104.

The alarm server 100 and user device 104 may be connected to a network108, which may be any suitable communications network such as a LAN,WAN, or the Internet. The user device 104 may thus communicate with thealarm server 100 via the network 108. In a preferred embodiment, thealarm server 100 is a node in a networked computing environment, e.g.,such as node 10 in cloud computing environment 50 shown in FIG. 2, andprovides cloud-based services to the user device 104.

With continued reference to FIG. 4, the computing environment may alsoinclude a wearable device 110. In embodiments, the wearable device 110is a wearable computing device, such as a smart watch, that includes aprocessing unit, memory, display, user input device (e.g., touch screenand/or physical buttons), rechargeable battery, sound emitting device(e.g., speaker), and antenna for wireless communication. The wearabledevice 110 may further comprise at least one sensor that is configuredto detect a sleep stage of a user wearing the wearable device 110. Theat least one sensor may comprise, for example, a biometric sensor (e.g.,a heart rate sensor) and orientation sensors (e.g., an accelerometer anda gyroscope) from which data can be analyzed to determine a sleep stageof a person wearing the wearable device 110 (e.g., sleep stage one, two,three or four). In embodiments, the wearable device 110 and the userdevice 104 are paired and communicate with one another using Bluetooth,Near Field Communication (NFC), or other suitable protocol. In analternative embodiment, the user device 104 and the wearable device 110are implemented together as a single device, e.g., a single smart watchthat includes the alarm app 106 and the at least one sensor to detect auser's sleep stage.

Still referring to FIG. 4, in aspects the computing environment alsoincludes a networked appliance 112. In embodiments, the networkedappliance 112 comprises an Internet of Things (IoT) device that isconnected to the network 108 and controllable by another computingdevice via the network 108. The networked appliance 112 may comprise atelevision, stereo system, lamp, or thermostat control, to name but afew non-limiting examples. There may be more than one networkedappliance 112 associated with the user device 104 and connected to thenetwork 108. In embodiments, identification (ID) information of thenetworked appliance 112 is specified by a user of user device 104 viathe alarm app 106, and this identification information is provided tothe alarm server 100 so that the networked appliance 112 can becontrolled by or through the alarm server 100.

The environment of FIG. 4 may also include a landline telephone 114,which may be connected to the network 108 or alternatively to a publicswitched telephone network (not shown). In embodiments, the telephonenumber of the landline telephone 114 is specified by a user of userdevice 104 via the alarm app 106, and this telephone number is providedto the alarm server 100.

With continued reference to FIG. 4, the computing environment may alsoinclude a number of trusted user devices 118 a, 118 b, . . . , 118 n. Inembodiments, each trusted user device 118 a-n comprises a computingdevice such as a smartphone, smart watch, tablet computer, laptopcomputer, or desktop computer. Each trusted user device 118 a-n may alsobe connected to the network 108 for communicating with the alarm server100. In embodiments, contact information for each trusted user device118 a-n (e.g., telephone number, email address, etc.) is specified by auser of user device 104 via the alarm app 106, and this contactinformation is provided to the alarm server 100 so that the alarm server100 can contact one or more of the trusted user device 118 a-n duringcertain processes described herein.

In some implementations, the user device 104 and at least one of thenetworked device 112 and the landline telephone 114 are commonly locatedin a location 116 such as a house, apartment, hotel room, office, etc.When a wearable device 110 is used, it may also be at the location 116.

Embodiments of the invention may employ elements of the environment ofFIG. 4 for proactively and/or reactively handling a situation where abattery drain condition of the user device 104 will prevent the userdevice 104 from sounding an alarm at the set alarm time. Embodiments mayinclude, for example: sounding the alarm earlier than scheduled;providing a message simultaneously to plural other users (via trusteduser devices 118 a-n) to take action to provide an alternate alarm;providing a message to a highest ranked one of a plurality other usersto take action to provide an alternate alarm; automatically takingaction to provide an alternate alarm (i.e., without involving otherusers); warning a user, when the user is setting the alarm, that thereis a battery drain condition that may affect the alarm; and alerting auser, after the alarm is set but before the user has entered a deepsleep stage, that there is a battery drain condition that may affect thealarm. As used herein, a battery drain condition can refer to either:the battery charge level of the user device 104 dropping to or below apredefined level (e.g., 3%), or the battery charge level of the userdevice 104 dropping to or below a level that is insufficient to keep thedevice powered on until the set alarm time. As described herein, thebattery drain condition may be detected by the alarm app 106, e.g., byusing a battery status API (application program interface) or othermethod to ascertain charge level of the battery of the user device 104.

In a first embodiment, the user device 104 is configured to sound thealarm early (i.e., prior to the alarm time that was set by the user) ifone or more conditions are met. A condition may include, for example: atype of alarm (e.g., critical or non-critical), and a threshold amountof time relative to the set alarm time (e.g., how early the alarm can besounded compared to the set alarm time). In this embodiment, the usersets an alarm on their user device 104 using the alarm app 106, e.g., byspecifying an alarm time. The user may also specify other alarmsettings, such as an alarm date, alarm sound (e.g., ringtone, vibration,etc.), and alarm snooze settings. The user also uses the alarm app 106to specify at least one condition, e.g., type of alarm (e.g., criticalor non-critical), and threshold amount of time. The alarm app 106monitors the remaining battery charge of the user device 104 during thetime period between when the user set the alarm and the set alarm time.In the event the alarm app 106 detects a battery drain condition of theuser device 104 prior to the set alarm time, the alarm app 106 thendetermines whether the user-specified conditions are met. If theconditions are met, then the alarm app 106 causes the user device 104 tosound the alarm early, e.g., prior to the set alarm time.

As described herein, the conditions may include a threshold amount oftime that the user may specify in the settings of the alarm app 106. Inthis manner, the user may define a threshold amount of time in the alarmapp 106, and the system may be configured to sound the alarm early onlyif the battery drain condition is detected within the threshold amountof time relative to the set alarm time. For example, a user may set thethreshold time as one hour, and may set their alarm time as 7:00 AM. Ifthe system detects a battery drain condition at 6:30 AM (e.g., less thanone hour prior to 7:00 AM), then the system causes the user device 104to sound the alarm at 6:30 AM (e.g., prior to the actual set time of7:00 AM). On the other hand, if the system detects a battery draincondition at 2:30 AM (e.g., more than one hour prior to 7:00 AM), thenthe system will not cause the user device 104 to sound the alarm early.

In another embodiment, a user employs the alarm app 106 to define abackup alarm group of trusted users, e.g., other users identified from acontact list of the user device 104. Each member of the backup alarmgroup is associated with a trusted user device 118 a-n, and the contactinformation for each trusted user device 118 a-n (e.g., telephonenumber, email address) is provided by the user device 104 to the alarmserver 100. The user may also specify at least one of a networkedappliance 112 and a landline telephone 114 to the alarm app 106, whichforwards this information to the alarm server 100. In embodiments, thealarm server 100 stores information received from the user device 104(e.g., ID of backup alarm group and/or trusted user devices 118 a-n, IDof networked appliance 112, telephone number of landline telephone 114)in a profile or membership associated with the user device 104, e.g., aspart of a cloud service. Subsequently the user sets an alarm on theiruser device 104 using the alarm app 106, and the alarm app 106 monitorsthe battery charge of the user device 104. If the alarm app 106 detectsa battery drain condition prior to the set alarm time, then the alarmapp 106 communicates an alert to the alarm server 100. The alert mayinclude data that defines: the user device 104 (e.g., device ID and/orname or user associated with the user device 104); an indication of thedetected battery drain condition; and alarm settings (e.g., the setalarm time). The alarm app 106 may push the alert to the server based ondetecting the battery drain condition, or the server may pull the alertfrom the alarm app 106 during periodic monitoring of the alarm app 106.

In this embodiment, based on the alert from the user device 104 to thealarm server 100, the alarm server 100 sends a message to each trusteduser device 118 a-n in the user's defined backup alarm group. Themessage may include data defining the user device 104 (e.g., device IDand/or name or user associated with the device), alarm settings (e.g.,set alarm time), and an indication that the user device 104 is likely tofail to emit an alarm at the set alarm time. The message may alsoinclude an identification of the networked appliance 112 and/or thetelephone number of the landline telephone 114. The message may alsorequest that the trusted user perform one or more actions to provide analternate alarm to the user associated with the user device 104. Theaction to provide an alternate alarm may include, for example: knock ona door at the user's location 116; send a command to control thenetworked appliance 112; and call the user's landline telephone 114.Controlling the networked appliance 112 may include one of the trustedusers sending a command from one of the trusted user devices 118 a-n toturn on a stereo, lights, or television at the user's location 116, forexample.

In another embodiment, the alarm server 100 ranks the members of thebackup alarm group and sends the message to one member of the group at atime based on the ranking. Similar to the previously describedembodiment that utilizes the backup alarm group, the message in thisembodiment may include data defining the user device 104, alarmsettings, and an indication that the user device 104 is likely to failto emit an alarm at the set alarm time. The message may also include anidentification of the networked appliance 112 and/or the telephonenumber of the landline telephone 114. The message may also request thatthe trusted user perform one or more actions to provide an alternatealarm to the user associated with the user device 104, e.g., knock on adoor at the user's location 116; send a command to control a networkedappliance 112; and call the user's landline telephone 114. However, incontrast to the previously described embodiment that sends the messageto all members of the backup alarm group, this embodiment only sends themessage to one member at a time, i.e., the highest ranked member of thebackup alarm group that has not already been messaged. In thisimplementation, if a first member of the backup alarm group does notachieve the desired result (i.e., wake up the user associated with userdevice 104), then the alarm server 100 sends the message to the nexthighest ranked member of the backup alarm group. In embodiments, thesystem continues polling the members of the backup alarm groupindividually until the desired result is achieved. The members of thebackup alarm group may be ranked using any suitable parameters,including their GPS location (e.g., proximity of their trusted userdevice 118 a to the user device 104), and their alertness state (e.g.,whether the trusted user is awake or asleep, which may be detected usinga wearable device and/or the trusted user device 118 a).

In another embodiment, the alarm server 100 does not contact members ofa user-defined backup alarm group, but instead automatically takesaction to provide an alternate alarm to the user associated with theuser device 104 (e.g., to attempt to wake the user associated with theuser device 104). In this embodiment, the user sets an alarm on theiruser device 104 using the alarm app 106. The alarm app 106 then monitorsthe battery charge of the user device 104. In the event the alarm app106 determines a battery drain condition of the user device 104 prior tothe set alarm time, the alarm app 106 communicates this condition to thealarm server 100, e.g., either by push or pull communication aspreviously described. The alarm server 100 then provides an alternatealarm to the user by sending a command to control a networked appliance112 and/or calling the user's landline telephone 114.

In another embodiment, a proactive approach includes warning the user,when an alarm is being set by the user, that a battery drain conditionmay affect the alarm being set. In embodiments, the alarm app 106 isconfigured to determine an estimated remaining time (e.g., hours,minutes seconds) of battery charge of the user device 104. The alarm app106 may be programmed to make this determination alone or bycoordinating with a power management app of the user device 104. Theestimated remaining time may be determined in any suitable fashionincluding but not limited to: straight line extrapolation of time versuspercent battery remaining; historical battery usage (e.g., depletionrate) for this user device 104; and estimations of battery usage (e.g.,depletion rate) based on apps that are currently running on the userdevice 104. Based on the estimated remaining battery time, the alarm app106 may be configured to provide a warning message to the user when theuser is attempting to set the alarm, i.e., that there is insufficientbattery charge to keep the user device 104 powered to the desired alarmtime. The alarm app 106 may be configured to display a messagerequesting that the user plug in the user device 104 to charge thebattery. The alarm app 106 may be configured to prevent the user fromsetting the desired alarm, i.e., by not accepting a user input thatwould likely result in a failed alarm. After displaying the message, thealarm app 106 may be configured to save the alarm if it is detected thatthe user has plugged in the user device 104 for recharging the battery.

In another embodiment, the alarm app 106 is configured to cause an alertto the user when a battery drain condition of the user device 104 isdetected and when the user is detected as being in a predefined sleepstage. The alert may be provided by the user device 104 and/or thewearable device 110. In this embodiment, after the user sets an alarm onthe user device 104, the alarm app 106 monitors the battery level of theuser device and the wearable device 110 monitors the sleep stage of theuser. If a battery drain condition of the user device 104 is detectedconcurrently with the user being detected in a particular sleep stage(e.g., stage one), then the alarm app 106 causes an alert to occur tonotify the user of the battery drain condition before the user fallsinto a later sleep stage (e.g., stage two, three, or four). The alertmay comprise a vibration of the wearable device 110 that is felt by theuser. The alert may additionally or alternatively comprise a soundemitted by the user device 104 and/or the wearable device 110.

FIGS. 5-10 show flowcharts of methods in accordance with aspects of theinvention. The steps of FIGS. 5-10 may be implemented in the environmentof FIG. 4, for example, and are described using reference numbers ofelements depicted in FIG. 4. As noted above, the flowchart illustratesthe architecture, functionality, and operation of possibleimplementations of systems, methods, and computer program productsaccording to various embodiments of the present invention.

FIG. 5 shows a flowchart of a method in which the user device 104 isconfigured to sound an alarm early (i.e., prior to the set alarm time)when a battery drain condition is detected and when one or moreconditions are met. At step 501, the user sets preferences in the alarmapp 106. The preferences may include a condition comprising a thresholdamount of time that corresponds to how early the alarm is permitted tosound in the event of a low battery condition. The preferences mayinclude a condition comprising an indication of a first type of alarm(e.g., critical) for which early alert is permitted, and a second typeof alarm (e.g., non-critical) for which early alert is not permitted.Step 501 may include the user device 104 receiving and storing the userinput.

At step 502, the user sets the alarm using the alarm app 106 on the userdevice 104. Setting the alarm may include specifying an alarm time,alarm date, alarm sound, and type of alarm (e.g., critical ornon-critical). Step 502 may include the user device 104 receiving andstoring the user input.

At step 503, the alarm app 106 monitors the remaining battery charge ofthe user device 104. At step 504, the alarm app 106 determines whether abattery drain condition exists for the user device 104. In the event abattery drain condition is not detected, the process returns to step503. In the event a battery drain condition is detected, then at step505 the alarm app 106 evaluates the user preferences (from step 501) anddetermines whether the user-defined conditions are met. If theconditions are not met (e.g., the alarm type is the second type, or thecurrent time is not within the threshold amount of time relative to theset alarm time), then the process ends at step 506. If the conditionsare met (e.g., the alarm type is the first type, and the current time iswithin the threshold amount of time relative to the set alarm time),then at step 507 the alarm app 106 causes the user device 104 to emitthe alarm early (e.g., prior to the set alarm time).

FIG. 6 shows a flowchart of a method in which the system is configuredto alert a backup alarm group when a battery drain condition isdetected. At step 601, the user defines a backup alarm group in thealarm app 106, e.g., by selecting trusted users from a contact liststored in the user device 104. Step 601 may include the user device 104receiving and storing the user input.

At step 602, the user specifies alternate alarm devices in the alarm app106. The alternate alarm devices may comprise at least one of anetworked appliance 112 and a landline telephone 114. The step ofspecifying the alternate alarm devices may include providing a device IDof a networked appliance 112 and a telephone number of the landlinetelephone 114. Step 602 may include the user device 104 receiving andstoring the user input.

At step 603, the user device 104 sends data to the alarm server 100. Inembodiments, the data sent at step 603 includes an ID of members of thebackup alarm group, e.g., device ID's for trusted user devices 118 a-n.The data sent at step 603 may also include a device ID of a networkedappliance 112 and a telephone number of the landline telephone 114. Step603 may include the alarm server 100 receiving and storing this data ina profile or membership associated with the user or user device 104.

At step 604, the user sets the alarm using the alarm app 106 on the userdevice 104. Setting the alarm may include specifying an alarm time,alarm date, alarm sound, and type of alarm (e.g., critical ornon-critical). Step 604 may include the user device 104 receiving andstoring the user input.

At step 605, the alarm app 106 monitors the remaining battery charge ofthe user device 104. At step 606, the alarm app 106 determines whether abattery drain condition exists for the user device 104. In the event abattery drain condition is not detected, the process returns to step605. In the event a battery drain condition is detected, then at step607 the alarm app 106 sends data to the alarm server 100. The data maybe pushed by the user device 104 to the alarm server 100, or pulled bythe alarm server 100 as part of periodic monitoring of the user device104. The data sent at step 607 may define the user device 104, alarmsettings, and an indication of the detected battery drain condition,e.g., as described with respect to FIG. 4.

At step 608, the alarm server 100 sends a message to a trusted userdevice 118 a-n of each member of the backup alarm group. The message mayinclude data defining the user associated with the user device 104, theset alarm time, and an indication that the user device 104 is likely tofail to emit an alarm at the set alarm time. The message may alsoinclude the ID the networked appliance 112 and the telephone number ofthe landline telephone 114. The message may also request that thetrusted users perform one or more actions to provide an alternate alarmto the user associated with the user device 104, e.g., knock on a doorat the user's location 116, send a command to control a networkedappliance 112, or call the user's landline telephone 114, e.g., in amanner similar to that described with respect to FIG. 4.

FIG. 7 shows a flowchart of a method in which the system is configuredto alert individual members of a backup alarm group when a battery draincondition is detected. Steps 701-707 are similar to and may be performedin the same manner as steps 601-607, respectively.

At step 708, the alarm server 100 ranks the members of the backup alarmgroup that was defined at step 701. In embodiments, the alarm server 100generates a ranked list of the members based on at least one of: adetermined GPS location of each member (e.g., proximity of their trusteduser device 118 a to the user device 104), and a determined alertnessstate (e.g., whether the trusted user is awake or asleep, which may bedetected using a wearable device and/or the trusted user device 118 a).The ranking may also be based on type of alarm action as alternativebackups.

At step 709, the alarm server 100 send a message to the highest rankedmember of the backup alarm group according to the ranking from step 708.The message may be similar in content to the message described withrespect to step 608. However, at step 709, the message is sent to onlyone member of the backup alarm group, rather than being sent to allmembers of the group.

At step 710, the alarm server determines whether the desired result hasbeen achieved. For example, the alarm server may receive a communicationfrom the user that was messaged at step 709 that the user associatedwith user device 104 is awake. In another example, the alarm server maydetermine that the user associated with user device 104 is awake, e.g.,by detecting actions at the user device 104 and/or wearable device 110that are predefined as indicating an awake state of the user.

If the alarm server 100 determines that the user is awake at step 710,then the process ends at step 711. On the other hand, if the alarmserver 100 determines that the user is not awake at step 710, then atstep 712 the alarm server sends the message to the next highest rankedmember in the ranked list from step 708, and the process returns to step710.

FIG. 8 shows a flowchart of a method in which the system is configuredto automatically alert a user when a battery drain condition isdetected. At step 802, the user specifies alternate alarm devices usingthe alarm app 106. The alternate alarm devices may comprise at least oneof a networked appliance 112 and a landline telephone 114. The step ofspecifying the alternate alarm devices may include providing a device IDof a networked appliance 112 and a telephone number of the landlinetelephone 114. Step 802 may include the user device 104 receiving andstoring the user input.

At step 803, the user device 104 sends data to the alarm server 100. Inembodiments, the data sent at step 803 includes a device ID of anetworked appliance 112 and a telephone number of the landline telephone114. Step 803 may include the alarm server 100 receiving and storingthis data in a profile or membership associated with the user or userdevice 104.

At step 804, the user sets the alarm using the alarm app 106 on the userdevice 104. Setting the alarm may include specifying an alarm time,alarm date, alarm sound, and type of alarm (e.g., critical ornon-critical). Step 804 may include the user device 104 receiving andstoring the user input.

At step 805, the alarm app 106 monitors the remaining battery charge ofthe user device 104. At step 806, the alarm app 106 determines whether abattery drain condition exists for the user device 104. In the event abattery drain condition is not detected, the process returns to step805. In the event a battery drain condition is detected, then at step807 the alarm app 106 sends data to the alarm server 100. The data maybe pushed by the user device 104 to the alarm server 100, or pulled bythe alarm server 100 as part of periodic monitoring of the user device104. The data sent at step 807 may define the user device 104, alarmsettings, and an indication of the detected battery drain condition,e.g., as described with respect to FIG. 4.

At step 808, the alarm server 100 provides an alternate alarm using thealternate device(s) that were specified in step 802. For example, step808 may comprise the alarm server 100 sending a command to control anetworked appliance 112 (e.g., to turn on a stereo, light, or televisionin the location 116, or to turn off the air conditioning in the location116). As another example, step 808 may comprise the alarm server 100placing a call to the landline telephone 114.

FIG. 9 shows a flowchart of a method in which the system warns the userthat a battery drain condition may affect an alarm that is being set bythe user. At step 901, the user sets the alarm using the alarm app 106on the user device 104. Setting the alarm may include specifying analarm time, alarm date, alarm sound, and type of alarm (e.g., criticalor non-critical). Step 901 may include the user device 104 receiving andstoring the user input.

At step 902, the alarm app 106 determines an estimated remaining time(e.g., hours, minutes seconds) of battery charge of the user device 104.This may be performed in the manner described with respect to FIG. 4.

At step 903, the alarm app 106 determines whether a battery draincondition exists for the alarm (from step 901) based on the estimatedremaining time of battery charge (from step 902). If it is determinedthat a battery drain condition does not exist, then at step 904 thealarm app 106 saves the alarm (from step 901). If it is determined thata battery drain condition does exist, then at step 905 the alarm app 106provides a warning to the user. In embodiments, the warning comprises avisual display and/or sound emitted by the user device 104. In aparticular embodiment, the warning comprises a message displayed by theuser device 104, wherein the message indicates that there isinsufficient battery charge to keep the user device 104 powered to thedesired alarm time. The message may also instruct the user to plug inthe user device 104 to charge the battery of the user device 104.

At step 906, the alarm app 106 detects that the user device 104 isplugged in and that the battery of the user device 104 is charging.Based on the detecting at step 906, the process proceeds to step 904.

FIG. 10 shows a flowchart of a method in which the system provide analert to the user when a battery drain condition of the user device 104is detected and when the user is detected as being in a predefined sleepstage. At step 1001, the user device 104 and wearable device 110 arepaired, e.g., using Bluetooth, NFC, or other suitable protocol.

At step 1002, the user sets the alarm using the alarm app 106 on theuser device 104. Setting the alarm may include specifying an alarm time,alarm date, alarm sound, and type of alarm (e.g., critical ornon-critical). Step 1002 may include the user device 104 receiving andstoring the user input.

At step 1003, the alarm app 106 monitors the remaining battery charge ofthe user device 104. At step 1004, the alarm app 106 determines whethera battery drain condition exists for the user device 104. In the event abattery drain condition is not detected, the process returns to step1003. In the event a battery drain condition is detected, then at step1005 the system detects the sleep stage of the user. In embodiments, thewearable device 110 detects the current sleep stage of the user (e.g.,in a manner described with respect to FIG. 4) and communicates thedetected sleep stage to the user device 104.

At step 1006, the alarm app 106 determines whether the detected sleepstage (from step 1005) is acceptable. In embodiments, the user mayspecify which sleep stages are acceptable and which sleep stages are notacceptable, e.g., in the preferences of the alarm app. For example, auser may specify that sleep stage one is acceptable and that sleepstages two, three, and four are not acceptable. In embodiments, at step1006, the alarm app 106 compares the detected sleep stage (from step1005) to the predefined acceptable sleep stage(s). If the sleep stage isacceptable, then at step 1007 the alarm app 106 provides an alert to theuser. The alert may comprise a vibration of the wearable device 110 thatis felt by the user. The alert may additionally or alternativelycomprise a sound emitted by the user device 104 and/or the wearabledevice 110. On the other hand, if the sleep stage is determined as notacceptable as step 1006, then the process ends at step 1008.

In implementations of the invention, aspects of the differentembodiments and method may be used in combination with one another toprovide a multi-faceted backup system for an alarm on the user device.For example, a method may begin at step 901, and the alarm that is savedat step 904 may serve as the alarm that is saved at any of steps 502,604, 704, 804, or 1002. In another example, a method may proceed fromstep 507 (e.g., the conditions for early alert are not met) to themethod defined in one of FIGS. 6-8.

In embodiments, a service provider, such as a Solution Integrator, couldoffer to perform the processes described herein. In this case, theservice provider can create, maintain, deploy, support, etc., thecomputer infrastructure that performs the process steps of the inventionfor one or more customers. These customers may be, for example, anybusiness that uses technology. In return, the service provider canreceive payment from the customer(s) under a subscription and/or feeagreement and/or the service provider can receive payment from the saleof advertising content to one or more third parties.

In still additional embodiments, the invention provides acomputer-implemented method for performing one or more of the processesdescribed herein. In this case, a computer infrastructure, such ascomputer system/server 12 (FIG. 1), can be provided and one or moresystems for performing the processes of the invention can be obtained(e.g., created, purchased, used, modified, etc.) and deployed to thecomputer infrastructure. To this extent, the deployment of a system cancomprise one or more of: (1) installing program code on a computingdevice, such as computer system/server 12 (as shown in FIG. 1), from acomputer-readable medium; (2) adding one or more computing devices tothe computer infrastructure; and (3) incorporating and/or modifying oneor more existing systems of the computer infrastructure to enable thecomputer infrastructure to perform the processes of the invention.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A computer-implemented method comprising:receiving, by a computing device, preference data from a user device;receiving, by the computing device, a set alarm time of the user device;determining, by the computing device, an alert from the user deviceindicates that a battery drain condition of the user device will resultin a failed alarm at the set alarm time at the user device; based on thereceiving the alert, determining a ranked list of members of a backupalarm group specified in the preference data, wherein each member of themembers is ranked based on a proximity of each member of the members tothe user device and an alertness state of each member of the members;and sending a message to the highest ranked member in the ranked list,wherein the message instructs the highest ranked member to provide analternate alert to a user associated with the user device.
 2. The methodof claim 1, wherein: the computing device comprises a server; and theuser device comprises one of a smartphone, a smart watch, a tabletcomputer, and a laptop computer.
 3. The method of claim 1, wherein thebattery drain condition of the user device is based on at least one of:a battery charge level of the user device being less than or equal to apredefined level; and the battery charge level of the user device beinginsufficient to maintain the user device in a powered on state until theset alarm time.
 4. The method of claim 1, wherein the computing deviceincludes software provided as a service in a cloud environment.
 5. Themethod of claim 1, further comprising deploying a system for providing abackup alarm, comprising providing a computer infrastructure operable toperform the steps of claim
 1. 6. The method of claim 1, wherein aservice provider at least one of creates, maintains, deploys andsupports the computing device.
 7. The method of claim 1, wherein stepsof claim 1 are provided by a service provider on a subscription,advertising, and/or fee basis.
 8. A system comprising: a centralprocessing unit (CPU), a computer readable memory and a non-transitorycomputer readable storage medium, for storing program instructions thatexecuted by the CPU, associated with a computing device; programinstructions to receive, by the computing device, preference data from auser device; program instructions to receive, by the computing device, aset alarm time of the user device; program instructions to determine, bythe computing device, an alert from the user device indicates that abattery drain condition of the user device will result in a failed alarmat the set alarm time at the user device; program instructions to, basedon the receiving the alert, determine, by the computing device, a rankedlist of members of a backup alarm group specified in the preferencedata, wherein each member of the members is ranked based on a proximityof each member of the members to the user device and an alertness stateof each member of the members; and program instructions to send, by thecomputing device, a message to the highest ranked member in the rankedlist, wherein the message instructs the highest ranked member to providean alternate alert to a user associated with the user device.